Determining telecommunication subscriber metrics

ABSTRACT

Information associated with a communication is gathered at a switching point during the routing process to determine subscriber metric information associated with an active service identifier. The information relates to the originator of the communication and the target. The information is compared to a provider database to determine a carrier originally associated with the active service identifier. The information is then compared to a porting database to determine if the active service identifier was ported, and if so, to which carrier the active service identifier was ported. A determination can then be made regarding which carrier is associated with the active service identifier. The data may be aggregated for a large amount of switched communications, representing a large amount of active service identifiers for a given market. Thus, a number of subscribers for a given carrier in a given market may be determined.

BACKGROUND

Communications services have become an important part of modern life(e.g., phone service, internet service, text messaging service, pagingservice, GPS service, music service, gaming service, and the like), ashave the devices associated with the communications (e.g., telephones,including cellular telephones, computers, notebook computers, personaldigital assistants, music players, gaming systems and the like). As oneexample, cellular telephone usage has proliferated rapidly over the pastdecade. By some estimates, cellular telephone usage in the United Statesalone has grown from 34 million users in 1995 to over 200 million in2005.

The term subscriber may refer to an end user of a communication service,e.g., an end-user of phone service, internet service, text messagingservice, paging service, GPS service, music service, gaming service, orthe like. A subscriber of mobile telephone communication service may bereferred to as a mobile subscriber. For example, a mobile subscriber maybe associated with a phone number that the mobile subscriber uses with amobile communications device, such as a cellular telephone.

The terms cellular telephone and mobile telephone may be usedinterchangeably herein. Further, the term phone call may refer to anytype of phone call (e.g. a call from/to a cellular telephone, a callfrom/to a land line telephone, etc.).

The term carrier may refer to an entity that provides communicationservices to subscribers. For example, a carrier may route calls to orfrom a subscriber using networks owned or operated by the carrier and/orother networks.

Mobile subscribers may enter into an agreement for services with acarrier in order to be able to use associated cellular telephones.Further, carriers may compete to attract mobile subscribers.

Subscriber metrics describe characteristics of subscribers, especiallyas they relate to carriers. For example, subscriber metrics may estimatecarrier market share (e.g., the number of subscribers associated with agiven carrier in a market as a percentage of the total number ofsubscribers in the market), the number of subscribers associated with acarrier in a market, carrier chum rate, carrier activation rate (ornumber of activations for a carrier in a given period), carrierdeactivation rate (or number of deactivations for a carrier in a givenperiod), and the like.

By analyzing subscriber metrics, carriers may be better able to utilizemarketing resources. This may include being able to determine needs orpreferences of subscribers and offering products or services that appealto those needs or preferences.

Changes in subscriber metrics may happen over short periods of time.Carries may find it beneficial to be apprised of subscriber metricsoften and with little lag time. For example, if carriers are timelyinformed of changes in the needs or preferences of subscribers, carriersmay be able to reallocate resources in response to changing subscriberneeds or preferences.

Current methods of gathering and analyzing subscriber data to determinesubscriber metrics have many problems. For example, consider thefollowing examples illustrating problems with current methods ofdetermining mobile subscriber metrics, which may also have applicabilityto other communications services.

Subscriber metric data for public carriers may be available quarterly,but with a significant lag time. Carriers may desire timelier subscribermetrics, subscriber metrics for different periods of time, subscribermetrics for shorter time periods, subscriber metrics with less lag time,etc. For example, carriers may desire subscriber metrics over shorterperiods of time because mobile subscriber trends may take place in amuch shorter period than three months. Another example is that a carriermay want timely information before starting a marketing campaign.

Currently, subscriber metric data may only be available for certaingeographic regions. That is, subscriber metric data may be unavailablefor regions in which a carrier may be interested, such as data on aparticular county, city, sales market, etc.

Currently, another method to determine subscriber metrics is available.The other method uses sampling and/or querying to determine subscribermetrics (the “sampling/querying method”). The sampling/querying methodalso has many shortcomings.

The sampling/querying method begins by selecting a subset of numbersowned by a carrier and monitoring those numbers (i.e., a sample isselected from the possible universe of numbers associated with acarrier). The sample selection may be made from the Local ExchangeRouting Guide (LERG), which may identify numbers assigned to a carrier.

A problem with this step is that only a small subset of actual numbersis used. Using a subset of numbers as an estimate for total numbersintroduces error into the resulting subscriber metrics because theresulting estimates are not based on actual data. Further, as the sizeof the sampled subset of numbers decreases, the error introduced intothe resulting subscriber metrics may increase. Typically, thesampling/querying method uses less than 5% of actively assigned numbers.

Another problem with the sampling/querying method is that the sample setmay include a variable amount of inactive numbers (i.e., a number notcurrently assigned to a subscriber). For example, the LERG data simplystates which numbers may be assigned to a carrier. However, just becausea number was assigned to a carrier does not mean that the number is anactive number. By analyzing inactive numbers, resources are wasted.

Another problem with the sampling/querying method is the use of SS7queries to confirm subscriber information. The sampling/querying methoduses SS7 queries to determine information about a number. That is, underthe current method an SS7 query is sent out to a device associated withthe number for which the SS7 query was sent. The SS7 query typicallygets information about the number from an HLR.

Using SS7 queries to determine subscriber metrics is a waste ofresources. For example, by using an SS7 query one or more additionalsteps are needed in addition to the methods herein described. Inaddition an SS7 query adds an additional and unnecessary burden oncommunications networks because SS7 queries are routed throughcommunications networks.

Using SS7 queries to determine subscriber metrics introduces additionalinaccuracies into the subscriber metrics determined by thesampling/querying method. For example, SS7 queries determine mobilesubscriber information from data associated with HLR's. However,carriers do not keep data at the HLR level up to date. Becauseinformation at HLR's may be inaccurate, using SS7 queries introducesadditional inaccuracies into the subscriber metrics determined by thesampling/querying method.

Another problem with the sampling/querying method is that significantresearch and development must be performed before the method can be usedin a new geographic region. For example, SS7 querying for a geographicregion may only be meaningful if research is performed relating to thegeographic region.

Thus, there exists a need to improve upon current methods of providingsubscriber metrics.

SUMMARY

The disclosed embodiments provide systems and methods for determiningsubscriber metrics based on information gathered at switching points ofa communications network.

A communication, such as a phone call for example, may be routed througha network. As part of the routing, the communication may be switched ata switching point. A record of the communication, such as a call detailrecord associated with a phone call, may be created at the switchingpoint in the network. The record may comprise information fieldsrelating to the communication, including information fields thatidentify an active service identifier(s) associated with thecommunication. For example, for a phone call, a call detail record maycomprise active service identifiers, such as an originating phone numberand/or a target phone number.

Information in the record may be compared to one or more databases todetermine which carrier is associated with an identified active serviceidentifier. For example, still using a phone call example, a phonenumber (e.g., the originating phone number and/or target phone number)may be compared to a service provider number database (e.g., a databasethat identifies the carrier that was originally assigned to the number).An example of such a database is the Local Exchange Routing Guide(LERG). Thus, the carrier originally assigned to the phone number isdetermined.

The phone number may also be compared to a porting database (e.g., adatabase that identifies numbers that have been ported and the carrierinformation relating to the porting). An example of a porting databaseis the Local Number Portability (LNP) database. By comparing the phonenumber to the LNP, a determination of the carrier associated with thenumber may be performed. That is, the phone number may be associatedwith the carrier originally assigned to the phone number, unless theporting database indicates another carrier.

The carrier data may be aggregated to provide subscriber metrics. Forexample, as described above, a carrier may be associated with an activeservice identifier by using information from a switched communication.When switching a large number of communications, a large number ofactive service identifiers may be identified (e.g., a carrier may switcha large amount of communications in a particular market). Further, eachof the identified active service identifiers may have an associatedcarrier. By aggregating the active service identifiers associated with agiven carrier in a market, the number of subscribers for that carriermay be calculated (i.e., a number of subscribers for the given carrierin a particular market may be determined). In addition, by comparing theamount of subscribers associated with the given carrier in a market withthe total number of subscribers in the market, a market share for thegiven carrier may be determined.

The foregoing summary, as well as the following detailed description, isbetter understood when read in conjunction with the drawings. For thepurpose of illustrating the claimed subject matter, there is shown inthe drawings examples that illustrate various embodiments; however, theinvention is not limited to the specific systems and methods disclosed.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A illustrates an overview of an exemplary network environment inwhich aspects of one or more embodiments may be implemented.

FIG. 1B illustrates an exemplary GPRS network architecture in whichaspects of one or more embodiments may be implemented.

FIG. 2 illustrates an alternate block diagram of an exemplaryGSM/GPRS/IP multimedia network architecture in which aspects of one ormore embodiments may be implemented.

FIG. 3 illustrates an exemplary method of creating data relating tosubscribers based on communications routed through a network.

FIG. 4 illustrates an exemplary method to determine subscriber metricinformation.

FIG. 5 illustrates an exemplary method to determine deactivations.

FIG. 6 illustrates methods to determine subscriber metrics.

DETAILED DESCRIPTION

The detailed description that follows may refer to steps (i.e., portionsof a method). However, the disclosed steps and associated methods areexemplary. The order of the steps may be varied where appropriate. Inaddition, steps may be omitted if not needed and additional steps may beadded where appropriate.

The present disclosure describes with particular reference andapplication to mobile communications services, and in particular tomobile subscribers; however, the claimed embodiments are not intended tobe limited to mobile communications services or mobile subscribers. Theclaimed embodiments are equally applicable to any service capable ofperforming as herein described. For example, subscriber metrics may bedetermined as herein described for other services routed through anetwork (e.g., internet service, text messaging service, paging service,GPS service, music service, gaming service, and the like).

FIGS. 1A, 1B and 2 depict some example telephony radio networks andnon-limiting operating environments in which a call enhancement withlocalized information system may be implemented. The below-describedoperating environments should be considered non-exhaustive, however, andthus the below-described network architecture merely shows an examplenetwork architecture in which aspects of various embodiments may beincorporated. One can appreciate, however, that aspects of an embodimentmay be incorporated into now existing or future alternativearchitectures for communication networks.

The global system for mobile communication (“GSM”) is one of the mostwidely-used wireless access systems in today's fast growingcommunication systems. GSM provides circuit-switched data services tosubscribers, such as mobile telephone or computer users, for example.General Packet Radio Service (“GPRS”), which is an extension to GSMtechnology, introduces packet switching to GSM networks. GPRS uses apacket-based wireless communication technology to transfer high and lowspeed data and signaling in an efficient manner. GPRS optimizes the useof network and radio resources, thus enabling the cost effective andefficient use of GSM network resources for packet mode applications. Forpurposes of explanation, various embodiments are described herein inconnection with GSM. The references to GSM are not exclusive, however,as it should be appreciated that embodiments may be implemented inconnection with any type of wireless access system such as, for example,CDMA or the like.

As may be appreciated, the example GSM/GPRS environment and servicesdescribed herein can also be extended to 3G services, such as UniversalMobile Telephone System (“UMTS”), Frequency Division Duplexing (“FDD”)and Time Division Duplexing (“TDD”), High Speed Packet Data Access(“HSPDA”), cdma2000 1x Evolution Data Optimized (“EVDO”), Code DivisionMultiple Access-2000 (“cdma2000 3x”), Time Division Synchronous CodeDivision Multiple Access (“TD-SCDMA”), Wideband Code Division MultipleAccess (“WCDMA”), Enhanced Data GSM Environment (“EDGE”), InternationalMobile Telecommunications-2000 (“IMT-2000”), Digital Enhanced CordlessTelecommunications (“DECT”), etc., as well as to other network servicesthat shall become available in time. In this regard, the techniques ofthe various embodiments discussed below may be applied independently ofthe method of data transport, and does not depend on any particularnetwork architecture, or underlying protocols.

FIG. 1A depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network, in whichaspects of an embodiment may be practiced. In such an environment, theremay be any number of subsystems that implement the functionality of theenvironment such as, for example, a plurality of Base Station Subsystems(“BSS”) 100 (only one is shown in FIG. 1A), each of which comprises aBase Station Controller (“BSC”) 104 serving a plurality of BaseTransceiver Stations (“BTS”) such as, for example, the BTSs 101, 102 and103. BTSs 101, 102 and 103 may include antennas 101A, 102A and 103Arespectively. BTS's may be the access points where users of packet-basedmobile devices become connected to the wireless network. In anembodiment, the packet traffic originating from user devices (e.g.,cellular phones) is transported via an over the air interface to the BTS103, and from the BTS 103 to the BSC 104. Base station subsystems, suchas the BSS 100, may be a part of internal frame relay network 106 thatmay include Service GPRS Support Nodes (“SGSN”) such as the SGSN 105 and107. Each SGSN 105, 107, etc. may be in turn connected to an internalpacket network 108 through which the SGSN 105, 107, etc. can route datapackets to and from a plurality of gateway GPRS support nodes (GGSN)111, 110, etc.

As illustrated, the SGSN 107 and the GGSNs 111 and 110 may be part ofthe internal packet network 108. Gateway GPRS serving nodes 111 and 110may provide an interface to external Internet Protocol (“IP”) networkssuch as Public Land Mobile Network (“PLMN”) 115, corporate intranets117, a Fixed-End System (“FES”) and/or the public Internet 113 and/orthe like. As illustrated, subscriber corporate network 117 may beconnected to the GGSN 111 via a firewall 112; and the PLMN 115 may beconnected to the GGSN 111 via a boarder gateway router 114. A RemoteAuthentication Dial-In User Service (“RADIUS”) server 116 may be usedfor caller authentication when a user of a mobile cellular device callscorporate network 117, for example.

Generally, there may be four cell sizes in a GSM network—macro, micro,pico and umbrella cells. The coverage area of each cell is different indifferent environments. Macro cells may be regarded as cells where thebase station antenna is installed in a mast or a building above averageroof top level. Micro cells may be cells whose antenna height is underaverage roof top level; they are typically used in urban areas. Picocells may be small cells having a diameter is a few dozen meters; theymay be mainly used indoors. On the other hand, umbrella cells may beused to cover shadowed regions of smaller cells and fill in gaps incoverage between those cells.

FIG. 1B illustrates the architecture of a typical GPRS network assegmented into four areas: users 115, radio access network 120, corenetwork 124 and interconnect network 137. The users' area 115 mayinclude a plurality of end users. The radio access network 120 mayinclude a plurality of base station subsystems such as the BSSs 123,which include BTSs 121 and BSCs 122. The core network 124 may include ahost of various network elements. As illustrated here, the core network124 may include a Mobile Switching Center (“MSC”) 125, a Service ControlPoint (“SCP”) 126, a gateway MSC 127, a SGSN 130, a Home LocationRegister (“HLR”) 129, an Authentication Center (“AuC”) 128, a DomainName Server (“DNS”) 131 and a GGSN 132. The interconnect network 137also may include networks and network elements. As illustrated in FIG.1B, the interconnect network 137 may include a Public Switched TelephoneNetwork (“PSTN”) 133, a Fixed-End System (“FES”) and/or the Internet134, a firewall 135 and/or a Corporate Network 136.

A mobile switching center 125 may be connected to a large number of basestation controllers. At MSC 125, for example, depending on the type oftraffic, the traffic may be separated such that voice may be sent toPublic Switched Telephone Network (“PSTN”) 133 through Gateway MSC(“GMSC”) 127, and/or data may be sent to the SGSN 130, which then sendsthe data traffic to the GGSN 132 for further forwarding.

When the MSC 125 receives call traffic, for example, from the BSC 122,it may send a query to a database hosted by the SCP 126. The SCP 126 mayprocess the request and may issue a response to the MSC 125 so that itmay continue call processing as appropriate.

The HLR 129 may be a centralized database for users to register with theGPRS network. The HLR 129 may store static information about thesubscribers such as the International Mobile Subscriber Identity(“IMSI”), subscribed services, and/or a key for authenticating thesubscriber. The HLR 129 may also store dynamic subscriber informationsuch as the current location of the mobile subscriber. Associated withHLR 129 may be an AuC 128. The AuC 128 may be a database that containsthe algorithms for authenticating subscribers and may include theassociated keys for encryption to safeguard the user input forauthentication.

Any of the components described in relation to FIG. 1A may comprise aprocessor. A processor may include any hardware and/or softwarenecessary for operating and/or controlling the component and/orcomponents. A processor may have its own memory such as random accessmemory (RAM), register memory, cache memory, and the like. A processorassociated with a component may be in communication with one or more ofthe other components described in relation to FIG. 1A.

A processor may operate on computer-executable instructions.Computer-executable instructions may include computer-readableinstructions, for example machine code, byte code, script language,runtime code, and the like. The computer-executable instructions, whenexecuted by the processor, may for example cause the processor toperform one or more parts of the functions and methods herein described.

In the following, depending on context, the term “mobile subscriber” mayrefer to either the end user or to the actual portable device used by anend user of the mobile cellular service. When a mobile subscriber turnson a mobile device, the mobile device goes through an attach process bywhich the mobile device attaches to a SGSN of the GPRS network.Referring now to FIG. 1B, mobile subscriber 119 may initiate the attachprocess by turning on the network capabilities of the mobile device. Anattach request may be sent by the mobile subscriber 119 to the SGSN 130.The SGSN 130 may query another SGSN, to which the mobile subscriber 119may have been attached before, for the identity of the mobile subscriber119. Upon receiving the identity of the mobile subscriber 119 from theother SGSN, the SGSN 130 may request more information from the mobilesubscriber 119. This information may be used to authenticate the mobilesubscriber 119 to the SGSN 130 by the HLR 129. Once the mobilesubscriber 119 is verified, the SGSN 130 may send a location update tothe HLR 129 indicating the change of location to a new SGSN, in thiscase the SGSN at 130. The HLR 129 may notify the old SGSN, to which themobile subscriber 119 was attached, to cancel the location process forthe mobile subscriber 119. The HLR 129 may then notify the SGSN 130 thatthe location update has been performed. At this time, the SGSN 130 maysends an “Attach Accept” message to the mobile subscriber 119, which inturn, may send an “Attach Complete” message to the SGSN 130.

After the attaching process, the mobile subscriber 119 may enter anauthentication process. In the authentication process, the SGSN 130 maysend authentication information to the HLR 129, which may sendinformation back to the SGSN 130 based on the user profile that was partof the user's initial setup. The SGSN 130 may then send a request forauthentication and ciphering to the mobile subscriber 119. The mobilesubscriber 119 may use an algorithm to send the user identification (ID)and/or a password to the SGSN 130. The SGSN 130 may use the samealgorithm to compare the result. If a match occurs, the SGSN 130 mayauthenticate the mobile subscriber 119.

Next, the mobile subscriber 119 may establish a user session with thedestination network, for example, the corporate network 136, by goingthrough a Packet Data Protocol (“PDP”) activation process. The mobilesubscriber 119 may request access to the Access Point Name (“APN”), forexample, UPS.com, and the SGSN 130 may receive the activation requestfrom the mobile subscriber 119. The SGSN 130 may then initiate a DomainName Service (“DNS”) query to learn which GGSN node has access to theUPS.com APN. The DNS query may be sent to the DNS server 131 within thecore network 124 which may be provisioned to map to one or more GGSNnodes in the core network 124. Based on the APN, the mapped GGSN 132 mayaccess the requested corporate network 136. The SGSN 130 may then sendto the GGSN 132 a Create Packet Data Protocol (“PDP”) Context Requestmessage. The GGSN 132 may send a Create PDP Context Response message tothe SGSN 130, which may then send an Activate PDP Context Accept messageto the mobile subscriber 119.

Once activated, data packets of the call made by the mobile subscriber119 may then go through radio access network 120, core network 124, andinterconnect network 137, to reach corporate network 136.

Any of the components described in relation to FIG. 1B may comprise aprocessor. A processor may include any hardware and/or softwarenecessary for operating and/or controlling the component and/orcomponents. A processor may have its own memory such as random accessmemory (RAM), register memory, cache memory, and the like. A processorassociated with a component may be in communication with one or more ofthe other components described in relation to FIG. 1B.

A processor may operate on computer-executable instructions.Computer-executable instructions may include computer-readableinstructions, for example machine code, byte code, script language,runtime code, and the like. The computer-executable instructions, whenexecuted by the processor, may for example cause the processor toperform one or more parts of the functions and methods herein described.

FIG. 2 shows an example block diagram view of a GSM/GPRS/IP multimedianetwork architecture 138. As illustrated, the architecture 138 of FIG. 2includes a GSM core network 154, a GPRS network 157 and/or an IPmultimedia network 159. The GSM core network 154 may include a MobileStation (MS) 140, at least one Base Transceiver Station (BTS) 141,and/or a Base Station Controller (BSC) 142. The MS 140 may be MobileEquipment (ME), such as a mobile phone and/or a laptop computer that isused by mobile subscribers, with a Subscriber identity Module (SIM). TheSIM may include an International Mobile Subscriber Identity (IMSI),which may include a unique identifier of a subscriber. The BTS 141 maybe physical equipment, such as a radio tower, that enables a radiointerface to communicate with the MS 140. Each BTS may serve more thanone MS 140. The BSC 142 may manage radio resources, including the BTS141. The BSC 142 may be connected to several BTS 141. The BSC 142 andBTS 141 components, in combination, are generally referred to as a basestation (BS) and/or a radio access network (RAN) 143.

The GSM core network 154 may include a Mobile Switching Center (MSC)144, a Gateway Mobile Switching Center (GMSC) 145, a Home LocationRegister (HLR) 146, a Visitor Location Register (VLR) 147, anAuthentication Center (AuC) 148, and an Equipment Identity Register(EIR) 149. The MSC 144 may perform a switching function for the network.The MSC may perform other functions, such as registration,authentication, location updating, handovers, and call routing. The GMSC145 may provide a gateway between the GSM network and other networks,such as an Integrated Services Digital Network (ISDN) or a PublicSwitched Telephone Network (PSTN) 150. In other words, the GMSC 145 mayprovide interworking functionality with external networks.

The HLR 146 may include a database that contains administrativeinformation regarding each subscriber registered in a corresponding GSMnetwork. The HLR 146 may contain the current location of each mobilesubscriber. The VLR 147 may include a database that contains selectedadministrative information from the HLR 146. The VLR may containinformation necessary for call control and provision of subscribedservices for each mobile subscriber currently located in a geographicalarea controlled by the VLR 147. The HLR 146 and the VLR 147, togetherwith MSC 144, may provide call routing and roaming capabilities of theGSM network. The AuC 148 may provide parameters for authenticationand/or encryption functions. Such parameters may allow verification of asubscriber's identity. The EIR 149 may store security-sensitiveinformation about the mobile equipment.

The Short Message Service Center (SMSC) 151 may allow one-to-one ShortMessage Service (SMS) messages to be sent to/from the mobile subscriber140. For example, the Push Proxy Gateway (PPG) 152 may be used to “push”(i.e., send without a synchronous request) content to mobile subscriber119. The PPG 152 may act as a proxy between wired and wireless networksto facilitate pushing of data to MS 140. Short Message Peer to Peer(SMPP) protocol router 153 may be provided to convert SMS-based SMPPmessages to cell broadcast messages. SMPP may include a protocol forexchanging SMS messages between SMS peer entities such as short messageservice centers. It may allow third parties, e.g., content supplierssuch as news organizations, to submit bulk messages.

To gain access to GSM services, such as speech, data, and short messageservice (SMS), the MS 140 may first register with the network toindicate its current location by performing a location update and IMSIattach procedure. MS 140 may send a location update including itscurrent location information to the MSC/VLR, via the BTS 141 and the BSC142. The location information may then be sent to the MS's HLR. The HLRmay be updated with the location information received from the MSC/VLR.The location update may also be performed when the MS moves to a newlocation area. Typically, the location update may be periodicallyperformed to update the database as location updating events occur.

GPRS network 157 may be logically implemented on the GSM core networkarchitecture by introducing two packet-switching network nodes, aserving GPRS support node (SGSN) 155 and a Gateway GPRS support node(GGSN) 156. The SGSN 155 may be at the same hierarchical level as theMSC 144 in the GSM network. The SGSN may control the connection betweenthe GPRS network and the MS 140. The SGSN may also keep track ofindividual MS locations, security functions, and access controls.

The Cell Broadcast Center (CBC) 171 may communicate cell broadcastmessages that are typically delivered to multiple users in a specifiedarea. A Cell Broadcast may include a one-to-many geographically focusedservice. It may enable messages to be communicated to multiple mobilephone customers who are located within a given part of its networkcoverage area at the time the message is broadcast.

The GGSN 156 may provides a gateway between the GPRS network and apublic packet network (PDN) or other IP networks 158. That is, the GGSNmay provide interworking functionality with external networks, and mayset up a logical link to the MS through the SGSN. When packet-switcheddata leaves the GPRS network, it is transferred to external TCP-IPnetwork 158, such as an X.25 network or the Internet. In order to accessGPRS services, the MS first attaches itself to the GPRS network byperforming an attach procedure. The MS then activates a packet dataprotocol (PDP) context, thus activating a packet communication sessionbetween the MS, the SGSN, and the GGSN.

In a GSM/GPRS network, GPRS services and GSM services may be used inparallel. The MS may operate in one three classes: class A, class B, andclass C. A class A MS may attach to the network for both GPRS servicesand GSM services simultaneously. A class A MS may also supportsimultaneous operation of GPRS services and GSM services. For example,class A mobiles may receive GSM voice/data/SMS calls and GPRS data callsat the same time. The class B MS may attach to the network for both GPRSservices and GSM services simultaneously. However, the class B MS maynot support simultaneous operation of the GPRS services and GSMservices. That is, the class B MS may use one of the two services at agiven time. A class C MS may attach to one of the GPRS services and GSMservices at a time. A class C MS can attach for only one of the GPRSservices and GSM services at a time. Simultaneous attachment andoperation of GPRS services and GSM services is not possible with a classC MS.

The GPRS network 157 may be designed to operate in three networkoperation modes (NOM1, NOM2 and NOM3). A network operation mode of aGPRS network may be indicated by a parameter in system informationmessages transmitted within a cell. The system information messages maydictate to a MS where to listen for paging messages and how signaltowards the network. The network operation mode may represent thecapabilities of the GPRS network. In a NOM1 network, a MS may receivepages from a circuit switched domain (voice call) when engaged in a datacall. The MS may suspend the data call or take both simultaneously,depending on the ability of the MS. In a NOM2 network, a MS may notreceive pages from a circuit switched domain when engaged in a datacall, since the MS is receiving data and is not listening to a pagingchannel In a NOM3 network, a MS may monitor pages for a circuit switchednetwork while receiving data and vise versa.

IP multimedia network 159 was introduced with 3GPP Release 5, andincludes IP multimedia subsystem (IMS) 160 to provide rich multimediaservices to end users. A representative set of the network entitieswithin IMS 160 are a call/session control function (CSCF), media gatewaycontrol function (MGCF) 162, media gateway (MGW) 165, and a mastersubscriber database, referred to as a home subscriber server (HSS) 168.HSS 168 may be common to GSM network 154, GPRS network 157 as well as IPmultimedia network 159.

IP multimedia system 160 is built around the call/session controlfunction, of which there are three types: interrogating CSCF (I-CSCF)164, proxy CSCF (P-CSCF) 161 and serving CSCF (S-CSCF) 163. P-CSCF 161may be the MS's first point of contact with IMS 160. P-CSCF 161 forwardssession initiation protocol (SIP) messages received from the MS to anSIP server in a home network (and vice versa) of the MS. P-CSCF 161 mayalso modify an outgoing request according to a set of rules defined bythe network operator (for example, address analysis and potentialmodification).

The I-CSCF 164 may be an entrance to a home network, may hide the innertopology of the home network from other networks, and may provideflexibility for selecting an S-CSCF. The I-CSCF 164 may contactsubscriber location function (SLF) 169 to determine which HSS 168 to usefor the particular subscriber, if multiple HSSs 168 are present. TheS-CSCF 163 may perform the session control services for the MS 140. Thisincludes routing originating sessions to external networks and routingterminating sessions to visited networks. S-CSCF 163 may also decidewhether application server (AS) 167 is required to receive informationon an incoming SIP session request to ensure appropriate servicehandling. This decision may be based on information received from HSS168 (or other sources, such as application server 167). The AS 167 alsocommunicates to location server 170 (e.g., a Gateway Mobile LocationCenter (GMLC)) that provides a position (e.g., latitude/longitudecoordinates) of the MS 140.

The HSS 168 may contain a subscriber profile and may keep track of whichcore network node is currently handling the subscriber. It may alsosupport subscriber authentication and authorization functions (AAA). Innetworks with more than one HSS 168, a subscriber location functionprovides information on HSS 168 that contains the profile of a givensubscriber.

The MGCF 162 may provide interworking functionality between SIP sessioncontrol signaling from IMS 160 and ISUP/BICC call control signaling fromthe external GSTN networks (not shown). It also may control the mediagateway (MGW) 165 that provides user-plane interworking functionality(e.g., converting between AMR- and PCM-coded voice). The MGW 165 maycommunicate with other IP multimedia networks 166.

The Push to Talk over Cellular (PoC) capable mobile phones may registerwith the wireless network when the phones are in a predefined area(e.g., job site, etc.). When the mobile phones leave the area, they mayregister with the network in their new location as being outside thepredefined area. This registration, however, may not indicate the actualphysical location of the mobile phones outside the pre-defined area.

Any of the components described in relation to FIG. 2 may comprise aprocessor. A processor may include any hardware and/or softwarenecessary for operating and/or controlling the component and/orcomponents. A processor may have its own memory such as random accessmemory (RAM), register memory, cache memory, and the like. A processorassociated with a component may be in communication with one or more ofthe other components described in relation to FIG. 2.

A processor may operate on computer-executable instructions.Computer-executable instructions may include computer-readableinstructions, for example machine code, byte code, script language,runtime code, and the like. The computer-executable instructions, whenexecuted by the processor, may for example cause the processor toperform one or more parts of the functions and methods herein described.

FIG. 3 illustrates an exemplary method of creating a data recordrelating to a communication routed through a network. At 302, acommunication may be initiated. For example, a phone call to/from amobile subscriber may be initiated.

At 304, the communication may be routed through a network. Thecommunication may be a phone call routed through a network fortransmitting phone calls, such as the networks described in relation toFIGS. 1A, 1B and 2. For example, the call may be received/switched at acell tower and routed through a network; that is, there may be a switchassociated with the cell tower that serves to switch the call along toits destination. (see FIG. 1B and FIG. 2 for example).

An example of a call routed through a cellular telephone network may bea call placed from one mobile subscriber to another mobile subscriber.Another example may be a call placed to/from a mobile subscriber from/toa land line phone. Still another example may be a call placed to/from asatellite phone from/to a mobile subscriber. That is, a network thatswitches cellular telephone calls may be involved whenever one of theparties on a call is a mobile subscriber.

Components of the network may create a data record. At 306, a record maybe created relating to the communication. The record may containmultitudinous information fields. For example, the communication may bea phone call and the record may be a Call Detail Record (CDR). A CDR mayinclude information such as the phone number placing the call (i.e., theoriginating phone number), the subscriber associated with theoriginating number, the phone number receiving the call (i.e., thetarget phone number), the subscriber associated with the target phonenumber, the duration of the call, cell tower information, RFinterference encountered during the call, etc.

The record may be created and/or recorded by routing componentsassociated with routing the communication (e.g., BTS's 101, 102, 103,123, 141, BSC's 122, 142, etc.). Using the phone call example, a CDR maybe opened when a call connects with a cell tower where the call ispassed through a switch. When the call is completed, the CDR may beclosed. Further, there may be several different CDR's created for anygiven call depending on packet types, transferring the call from onetower to another, etc. Further, the CDR may be created for purposesother than determining subscriber metrics (e.g., billing), which mayavoid redundant creation of data.

At 308, the record may be sent to a server, e.g., a CDR may be sent to aserver (CDR data may be streamed from a cell tower switch to a server).For example, because there may be many switching points in a network,CDR's may be forwarded to a server from many different locations. Itshould be noted that the routing function may be performed by anyequipment capable of performing as herein described.

At 310, records may be standardized. For example, CDR information may bestandardized. Standardization may be helpful because the server mayreceive multiple records that have different attributes, such asdifferent formatting and/or non-standardized information fields. Thismay be likely to occur where records are sent to the server fromdifferent locations and/or types of equipment. For example, differentswitch manufacturers may have different standards for records.

FIG. 4 illustrates an exemplary method to determine subscriber metricinformation based on information in a record. At 412, an active serviceidentifier(s) may be identified (e.g., the record may identify theactive service identifier). The active service identifier may relate toa service provided by a carrier. For example, a phone number may be aservice identifier associated with phone service provided by a carrier,an internet service user account number may be a service identifier ofinternet service provided by a carrier, etc. An active serviceidentifier may refer to a service identifier that was used inassociation with the service for which a record was created. Forexample, a phone number may be identified as an originating number or atarget number in a CDR associated with a switched call; and thus, thephone number may be an active phone number. That is, if a calloriginated from a mobile subscriber, the number associated with theoriginating mobile subscriber may be an active number. Likewise, if acall was received by a mobile subscriber, the number associated with thereceiving mobile subscriber may be an active number. An active phonenumber may be an active service identifier.

An active service identifier may be compared to one or more databases todetermine which carrier is associated with the active serviceidentifier. In this way a number of active service identifiersassociated with a given carrier may be determined. At 414-418, anexample is illustrated using the phone call example.

At 414, for a phone number identified in a CDR, a determination may bemade as to which carrier the number was first assigned. One way todetermine the carrier originally assigned to a number is to compare thenumber with data from the Local Exchange Routing Guide (LERG).

The LERG identifies which carrier was assigned a particular block ofnumbers. By comparing a number to the LERG, a determination may be madeas to which carrier was originally associated with the number.

At 416, a determination may be made as to whether the number was portedfrom the original carrier to another carrier. One way to determinewhether a number was ported away from the originally assigned carriermay be to compare the number with Local Number Portability (LNP) data.

At 418, the carrier associated with the number may be determined. Stillusing the phone call example, if there is no record in the LNP data thata number has been ported, it may be assumed that the number may beassociated with the originally assigned carrier. Likewise, if the LNPindicates that the number has been ported to a carrier, it may beassumed that the carrier listed in the LNP (i.e., the ported carrier) isthe present carrier associated with the number.

The subscriber metric information gathered as described in FIG. 4 may berepeated for many switched communications identifying many activeservice identifiers. Further, data may be gathered for a particularperiod of time. For example, the data may be gathered weekly,bi-monthly, monthly, etc. The time periods used for gathering andorganizing the information is a matter of design choice.

Using the systems and methods herein disclosed may provide distinctadvantages over the prior art. By using active service identifiers, thedisclosed systems and methods may eliminate researching unassigned orinaccurately labeled service identifiers. Referring back to the exampleof the phone call, because the prior art uses blocks of assigned numbersthat may or may not be active and may or may not be correctly assigned,resources are wasted. Because the methods herein described do notresearch active service identifiers that may be inactive or incorrectlyassigned, the present methods may be more efficient than the prior art.

Another advantage is that the error introduced by statistical analysisis reduced. Because data may be gathered for a high percentage of activeservice identifiers, the error introduced by estimating subscribermetrics from only a small amount of data may be reduced.

Another advantage is that it is easier for a carrier to perform its ownanalysis and may avoid using a third party that does not have in-depthknowledge of the carrier's marketing goals and may have conflicts ofinterest with the carrier (e.g., conflicts arising from providingsubscriber metrics to multiple carriers).

Referring back to 304 in FIG. 3, and using the phone call example, CDRinformation is created for calls that interact with a network. There isa multiplication effect for carriers that route calls. That is, acarrier can access information not only for subscribers associated withthe carrier, but also from other subscribers associated with othercarriers. For example, consider a call from one mobile subscriberassociated with a first carrier to another mobile subscriber associatedwith a second carrier. The call may be routed at some point by the firstcarrier to the second carrier. Further, the first carrier may haveaccess to information about both subscribers from the CDR. Thus, thefirst carrier may receive information for more than just its ownsubscribers. Due to the multiplication effect, large carriers may beable to access information for a large majority of active subscribers.

Another advantage is that SS7 queries are not necessary. The data onactive service identifiers is generated as communications are routed.Thus, separate SS7 queries are not needed. Thus, less computingresources may be needed. In addition, a carrier may not add additionalload to networks by making SS7 queries.

Additional features may be added to the methods described in relation toFIG. 4 in order to track additional subscriber information. For example,FIG. 5 illustrates an exemplary method to determine deactivations.

At 520, present records may be compared to past records, e.g., presentCDR data may be compared to past CDR data. For example, a phone numbermay have been an active phone number in previous data sets as indicatedby past CDR's. However, the phone number may not appear in the currentdata set.

At 522, service identifiers may be identified that were in previous datasets, but not in current data sets, e.g., phone numbers may beidentified that were in previous data sets, but not in current data sets(i.e., missing numbers). For example, CDR data sets may be available forthe first four weeks of a year. A number may have been present in one ormore of weeks one through three. However, the number may not be presentin the CDR data set for week four.

At 524, trends may be identified in past data for service identifiers.The identified trends may aid in assessing deactivations. At 526, adetermination may be made as to whether the identified serviceidentifiers have been deactivated. Statistical analysis, algorithmsand/or set thresholds may be used to determine if an identified serviceidentifiers has been deactivated.

Consider the following examples relating to phone calls. For numbersshowing no activity for two weeks, the number may be considereddeactivated if the number was used to make and/or receive an average of20 calls per week for the three months prior to inactive period. Anotherrule may be used for numbers that may have been inactive for four weeks,but may not have been classified as deactivated by the two week data.For example, for numbers showing no activity for four weeks, the numbermay be considered deactivated if the number was used to make and/orreceive an average of 10 calls per month for the three months prior toinactive period. Another rule may be used for numbers that may have beeninactive for twelve weeks, but may not have been classified asdeactivated by the two or four week data. For example, for numbersshowing no activity for twelve weeks, the number may be considereddeactivated if the number was used to make and/or receive an average of10 calls per quarter for the three months prior to inactive period.

The foregoing examples are matters of design choice. Irrespective of thedesign choice, a carrier may set rules to determine deactivations fromtrends in records, such as CDR data.

At 528, a backcheck of service identifiers errantly identified asdeactivated may be performed. Using the phone call example, a number mayhave been identified as deactivated (e.g., a number may have satisfiedone of the above examples). However, the number previously identified asdeactivated may be listed in the present data set as an active number,still associated with the same subscriber and the same carrier as thelast time it was active (e.g. calling patterns are the same). Thus, thenumber may have been errantly identified as deactivated.

Time limits may be placed on the amount of time that passes for aservice identifier to still be considered errantly identified asdeactivated. For example, if a year passed with no activity from theservice identifier, the service identifier may not be considerederrantly identified as deactivated.

At 530, a correction process may be performed. The correction processmay base a correction on such things as trends in record data or serviceidentifiers errantly identified as deactivated at 528. Using the phonecall example, trends in CDR data may reveal that a certain month mayhave many more numbers without activity than other months, increasingthe chance of errantly identifying numbers as deactivated. Adjustmentsmay be performed to make an allowance for such a trend. A correctionprocess may be performed to adjust the determination at 526 to be lessstringent (i.e., require a passage of more time before a serviceidentifier is identified as deactivated).

Another example may be a phone number that has only sporadic activitywith lengthy periods of inactivity between uses. Such a mobilesubscriber may be a “glovebox user,” that is, a mobile subscriber thatmay keep a phone for emergencies or specific functions and does not usethe number in a consistent way. If a number is identified as being usedonly in such a sporadic manner, a correction process may be performed toadjust the determination at 526 to be less stringent or to remove thenumber from consideration as a deactivated number.

The foregoing examples are matters of design choice. Irrespective of thedesign choice, records may be used to identify trends to makecorrections to the process.

FIG. 6 illustrates methods to determine subscriber metrics byaggregating data. At 632, subscriber metrics may be determined foractive service identifiers. Referring back to FIG. 4, at 412-418subscriber metric information is determined (e.g., a carrier associatedwith an active service identifier is identified).

At 632, carrier determinations may be aggregated to provide a number ofservice identifiers/subscribers associated with a given carrier. Forexample, the determination made in FIG. 4 (e.g., at 418) may be repeatedfor a large amount of communications. The large amount of communicationsmay identify a large amount of active service identifiers. Asillustrated in FIG. 4, a carrier associated with each of the activeservice identifiers may be identified. Further, each of the activeservice identifiers associated with a first carrier may be aggregated.That is, by adding together each subscriber associated with the firstcarrier, a number of subscribers associated with the first carrier maybe determined. Likewise, each of the active service identifiersassociated with a second carrier may be aggregated resulting in a numberof subscribers associated with the second carrier. This process may berepeated for other carriers. The carrier subscriber data may be used todetermine other subscriber metrics.

The carrier subscriber data may also be used to determine a market sharefor a carrier. For example, a market share for the first carrier may bedetermined by calculating the ratio of the number of subscribersassociated with the first carrier in a market to a total number ofsubscribers in the market.

At 634, subscriber metrics may be determined based upon analysis ofpresent record data compared to past record data. For example, FIG. 5illustrates determining a deactivation based on such data. Byaggregating such data, subscriber metrics may be created for absolutenumbers of deactivations per carrier, percentage of deactivations percarrier, etc.

At 636, statistical analysis and/or extrapolation of the subscribermetrics determined at 632 and/or 634 may be used to calculate subscribermetrics for the rest of a market (e.g., national market, regionalmarket, local market, micromarket, etc.). At 632 and/or 634, subscribermetrics may have been calculated for a market. However, the subscribermetrics calculated at 632 and/or 634 may provide data for active serviceidentifiers that were identified by switched communications. There maybe other active service identifiers in the market that were notswitched. That is, the subscriber metrics calculated at 632 and/or 634may represent less than all of the active serviceidentifiers/subscribers in a given market.

Statistical analysis may be performed on the data collected in order toestimate subscriber metrics for the part of the market not identified incommunications switched by the network. The statistical analysis may beas simple as extrapolating from the numbers calculated at 632 and/or 634to using detailed algorithms. As an example of the statistical analysisthat may be employed, algorithms may be used to estimate activity levelsof non-measured subscribers. Results may be reconciled againsthistorical patterns or national reported carrier data for example, thus,subscriber metrics for a market can be provided. The methods used toestimate subscriber metrics for the remaining active service identifiers(i.e., active service identifiers that were not routed through thenetwork) is a matter of design choice. Irrespective of design choice,the data at 632 and/or 634 may be processed to estimate data for activeservice identifiers that were not switched by a carrier's network.

At 638, the subscriber metrics determined at 632, 634 and/or 636 may becombined to provide subscriber metrics. For example, at 632 the numberof subscribers per carrier may be calculated for switched communicationsin a market (e.g., communications that were switched by a carrier'snetwork). At 636, the number of subscribers per carrier may becalculated for active service identifiers that were not identified byswitched communications in a market. The data at 632 and 636 may becombined to provide the total number of subscribers per carrier in amarket. Further, a market share for a given carrier may be calculated(e.g., a market share for a first carrier may be determined bycalculating the ratio of the number of subscribers associated with thefirst carrier in a market to a total number of subscribers in themarket).

Reference is made herein to the methods being performed by a carrierwith a network. However, the systems and methods disclosed herein arenot limited to implementation by a single carrier with a single network.For example, multiple carriers may share data. Further, a single carriermay have access to more than its own network.

Reference is made herein to records generated and used in order toprovide subscriber metrics. The creation of subscriber metrics as hereindescribed may be for particular periods of time. For example, recordsmay be created during a two week period. Further, subscriber metrics maybe created from the records, thus, providing subscriber metrics for thattwo week period. The time periods used for gathering and organizing theinformation is a matter of design choice.

What is claimed:
 1. A method comprising: receiving a plurality ofrecords, wherein each record of the plurality of records identifies asource active service identifier and a recipient active serviceidentifier, and wherein each record of the plurality of records isgenerated at a switching point in a network in response to a respectiverequest for a respective requested routed service associated with arespective source active service identifier; determining an associatedcarrier for each recipient active service identifier identified in eachof the plurality of records, wherein the associated carrier isdetermined by comparing each recipient active service identifier to (i)first information indicating that a respective service identifier isassigned to a respective carrier and to (ii) second informationassociated with local number portability; and determining a number ofrecipient active service identifiers for a first carrier by aggregatingeach recipient active service identifier associated with the firstcarrier.
 2. The method of claim 1, further comprising determining amarket share of active service identifiers for the first carrier.
 3. Themethod of claim 2, wherein the market share of active serviceidentifiers for the first carrier is determined by calculating a ratioof the number of recipient active service identifiers to a total numberof recipient active service identifiers identified in the plurality ofrecords.
 4. The method of claim 1, wherein each source active serviceidentifier is an active phone number.
 5. The method of claim 1, whereinthe plurality of records is collected from a network controlled by oneentity.
 6. The method of claim 1, wherein the plurality of records is aplurality of call detail records.
 7. The method of claim 1, wherein eachrecipient active service identifier is an active phone number.
 8. Themethod of claim 1, wherein each of the plurality of records comprisesthe first information and the second information.
 9. The method of claim1, further comprising determining a number of deactivated serviceidentifiers for the first carrier.
 10. A system comprising: at least onememory comprising instructions; and at least one computer processor incommunication with the at least one memory, wherein the at least onecomputer processor, when executing the instructions, effectuatesoperations comprising: receiving a plurality of records associated witha plurality of communications, wherein each record of the plurality ofrecords is generated at a switching point in a network in response to arespective request for a respective requested routed service associatedwith a respective source active service identifier, and wherein eachrecord of the plurality of records identifies a source active serviceidentifier and a recipient active service identifier; determining anassociated carrier for each recipient active service identifieridentified in each of the plurality of records, wherein the associatedcarrier is determined by comparing each recipient active serviceidentifier to (i) first information indicating that a respective serviceidentifier is assigned to a respective carrier and to (ii) secondinformation associated with local number portability; and determining anumber of recipient active service identifiers for a first carrier byaggregating each recipient active service identifier associated with thefirst carrier.
 11. The system of claim 10, wherein the operationsfurther comprise determining a market share of active serviceidentifiers for the first carrier.
 12. The system of claim 11, whereinthe market share of active service identifiers for the first carrier isdetermined by calculating a ratio of the number of recipient activeservice identifiers to a total number of recipient active serviceidentifiers identified in the plurality of records.
 13. The system ofclaim 10, wherein each source active service identifier is an activephone number.
 14. The system of claim 10, wherein the plurality ofrecords is collected from a network controlled by one entity.
 15. Thesystem of claim 10, wherein the plurality of records is a plurality ofcall detail records.
 16. The system of claim 10, wherein each recipientactive service identifier is an active phone number.
 17. The system ofclaim 10, wherein each of the plurality of records comprises the firstinformation and the second information.
 18. The system of claim 11,wherein the operations further comprise determining a number ofdeactivated service identifiers for the first carrier.
 19. The method ofclaim 1, wherein the operations further comprise obtaining the secondinformation from a local exchange routing guide.
 20. A computer-readablemedium that is not a transient signal, the computer-readable mediumcomprising computer-executable instructions to: receive a plurality ofrecords, wherein each record of the plurality of records identifies asource active service identifier and a recipient active serviceidentifier, and wherein each record of the plurality of records isgenerated at a switching point in a network in response to a respectiverequest for a respective requested routed service associated with arespective source active service identifier; determine an associatedcarrier for each recipient active service identifier identified in eachof the plurality of records, wherein the associated carrier isdetermined by comparing each recipient active service identifier to (i)first information indicating that a respective service identifier isassigned to a respective carrier and to (ii) second informationassociated with local number portability; and determine a number ofrecipient active service identifiers for a first carrier by aggregatingeach recipient active service identifier in which the associated carriercorresponds to the first carrier.
 21. The computer-readable medium ofclaim 20, wherein the plurality of records is a plurality of call detailrecords.